Perforce QAC Visual Studio Known Issues

The following list summarizes extant issues within Perforce QAC Visual Studio extension:

  • There is currently a limitation for Perforce QAC projects created from Validate whereby subsequently changing the Visual Studio build configuration and/or platform setting within the solution will not permit a suitable Perforce QAC project to be created for the new configuration. This will be remedied in a future release.
  • Perforce QAC project per active configuration

    • The Perforce QAC project is created only for the active configuration. If the active configuration is changed, a new Perforce QAC project needs to be created. This is a time-consuming activity which should be considered carefully.

  • Pure Visual Studio projects

    • From Visual Studio Integrated Development Environment, a Perforce QAC project can be created only for pure Visual Studio projects. Test projects are ignored.

  • Baseline suppression calculations can be wrong in Visual Studio 2017

    • Baseline suppression calculation can be wrong if the baseline copy includes files not encoded in UTF-8. As Visual Studio 2017 has changed the encoding of template files to UCS-2 LE BOM encoding this issue may happen unless all files are converted to UTF-8 encoding prior to a baseline copy being created. The workaround is to convert source files to UTF-8. This can be done by creating a .editorconfig file containing the following lines:

    root = true
    [*] 
    charset = utf-8

    The file should be put in the Visual Studio project folder or anywhere further up the folder tree. All newly created files or changed files will be in utf-8 encoding. Auto created files will need to be formatted (Ctrl+K,Ctrl+D).

  • QAC Explorer tool window folder order change

    • QAC Explorer tool window folder order change moves the Includes folder above the Source folder so if you have many header files the Source folder may be pushed out of view.

  • When upgrading the extension from 2019.1 it is possible to end up with two Perforce QAC extensions installed, causing the extension to become inoperable. This can be rectified by running a script to remove the errant extension:
    • C:\Perforce\QAC-<version>\scripts\PurgeOldVSExtension.cmd C:\Perforce\QAC-<version>